Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi all, for reference, this PR seeks to address issue #3. I wanted to start from an existing template to minimize the amount of work going into this issue and unfortunately, it seems that Jekyll templates are often proprietary. Instead, I decided to use a similar static site generator hugo. It's proven quite easy to use and had a great template to build our site off of.
You can find an example of the site running (same code & resources) here: https://nolski.github.io/example-librecorps-site/
There are still parts to fill in but I wanted to at least get the basics PR'd and submitted in order to get initial feedback.
Content Structure
As we have used markdown for majority of notes, I think keeping our notes in markdown is a good idea for now. We have six categories that we will be putting our resources into. You can find those categories below and the corrosponding resources:
Creating new resources
If you wish to create a new resource under a category. Simply create a new markdown file containing the info you wish to have in the resource. Make sure you prepend a header describing the resource as below: